Apparatus and methods for cell activation in wireless networks

ABSTRACT

Apparatus and methods for streamlined cell activation in a wireless network. In one embodiment, the apparatus and methods provide enhanced wireless services which utilize bandwidth-efficient setup/configuration messaging and cell activation, including for very large numbers of cells, and which do not overwhelm data backhaul(s) associated with wireless nodes used for communication. In one embodiment, a message protocol is used wherein a prescribed number of cells of a given DU (e.g., all, a prescribed subset, etc.) are activated without having to enumerate or include specific data relating to the cells being activated. In one variant, this “global” activation is conducted using an Activate All Cells IE (Information Element) disposed with the F1SETUP RESPONSE message issued by a controlling CU entity within a 5G-NR infrastructure. In other variants, cells of multiple DUs can be controlled simultaneously, such as via distribution of a system-wide global activation IE.

PRIORITY

This application claims priority to U.S. Provisional Patent applicationSer. No. 62/645,074 filed Mar. 19, 2018 and entitled “APPARATUS ANDMETHODS FOR CELL ACTIVATION IN WIRELESS NETWORKS,” which is incorporatedherein by reference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessdevices and networks thereof, and specifically in one exemplary aspectto activation or selection of one or more cells within one or more RANs(Radio Area Networks) of a radio network utilizing licensed and/orunlicensed spectrum.

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules). Currently only frequency bands between 9 kHzand 275 GHz have been allocated (i.e., designated for use by one or moreterrestrial or space radio communication services or the radio astronomyservice under specified conditions). For example, a typical cellularservice provider might utilize spectrum for so-called “3G” (thirdgeneration) and “4G” (fourth generation) wireless communications asshown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 Mbit/s). 1900 MHz PCS, Band 2 (UMTS/ HSPA+ up to 21Mbit/s). 4G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE).2300 MHz WCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency Center range Type frequency Availability Licensedusers 6.765 MHz- A 6.78 MHz Subject to local Fixed service & mobile6.795 MHz acceptance service 13.553 MHz- B 13.56 MHz Worldwide Fixed &mobile services 13.567 MHz except aeronautical mobile (R) service 26.957MHz- B 27.12 MHz Worldwide Fixed & mobile service 27.283 MHz exceptaeronautical mobile service, CB radio 40.66 MHz- B 40.68 MHz WorldwideFixed, mobile services & 40.7 MHz earth exploration-satellite service433.05 MHz- A 433.92 MHz only in Region amateur service & 434.79 MHz 1,subject to radiolocation service, local acceptance additional apply theprovisions of footnote 5.280 902 MHz- B 915 MHz Region 2 only Fixed,mobile except 928 MHz (with some aeronautical mobile & exceptions)radiolocation service; in Region 2 additional amateur service 2.4 GHz- B2.45 GHz Worldwide Fixed, mobile, 2.5 GHz radiolocation, amateur &amateur-satellite service 5.725 GHz- B 5.8 GHz WorldwideFixed-satellite, 5.875 GHz radiolocation, mobile, amateur &amateur-satellite service 24 GHz- B 24.125 GHz Worldwide Amateur,amateur-satellite, 24.25 GHz radiolocation & earth exploration-satelliteservice (active) 61 GHz- A 61.25 GHz Subject to local Fixed,inter-satellite, mobile 61.5 GHz acceptance & radiolocation service 122GHz- A 122.5 GHz Subject to local Earth exploration-satellite 123 GHzacceptance (passive), fixed, inter- satellite, mobile, space research(passive) & amateur service 244 GHz- A 245 GHz Subject to localRadiolocation, radio 246 GHz acceptance astronomy, amateur &amateur-satellite service

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs (e.g., Wi-Fi) andcordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1 5.15 to 5.25 GHz No UNII-2 5.25 to 5.35 GHz Yes UNII-2 Extended5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a node or “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

5G New Radio (NR) and NG-RAN (Next Generation Radio Area Network) NG-RANor “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G” nextgeneration radio system. 3GPP is currently specifying Release 15 NG-RAN,its components, and interactions among the involved nodes includingso-called “gNBs” (next generation Node B's or eNBs). NG-RAN will providehigh-bandwidth, low-latency wireless communication and efficientlyutilize, depending on application, both licensed and unlicensed spectrumof the type described supra in a wide variety of deployment scenarios,including indoor “spot” use, urban “macro” (large cell) coverage, ruralcoverage, use in vehicles, and “smart” grids and structures. NG-RAN willalso integrate with 4G/4.5G systems and infrastructure, and moreover newLTE entities are used (e.g., an “evolved” LTE eNB or “eLTE eNB” whichsupports connectivity to both the EPC (Evolved Packet Core) and the NR“NGC” (Next Generation Core).

In some aspects, Release 15 NG-RAN leverages technology and functions ofextant LTE/LTE-A technologies (colloquially referred to as 4G or 4.5G),as bases for further functional development and capabilities. Forinstance, in an LTE-based network, upon startup, an eNB (base station)establishes S1-AP connections towards the MME (mobility managemententity) whose commands the eNB is expected to execute. An eNB can beresponsible for multiple cells (in other words, multiple Tracking AreaCodes corresponding to E-UTRAN Cell Global Identifiers). The procedureused by the eNB to establish the aforementioned S1-AP connection,together with the activation of cells that the eNB supports, is referredto as the S1 SETUP procedure; see inter alia, 3GPP TS 36.413 V14.4.entitled “3rd Generation Partnership Project; Technical SpecificationGroup Radio Access Network; Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN); S1 Application Protocol (S1AP) (Release 14)” datedSeptember 2017, which is incorporated herein by reference in itsentirety.

As described in TS 36.413, per Section 9.1.8.4, the S1 SETUP REQUESTmessage is sent by the eNB to the target MME transfer information for aTNL association. See FIG. 1 herein. Per Section 9.1.8.5 of TS 36.413,the S1 SETUP RESPONSE message is sent by the MME to the transmitting eNBto transfer information for a TNL association. See FIG. 2 herein.

In the LTE/LTE-A standards, an eNB can support up to and including 256cells. So, including the identities of all the supported cells in an S1SETUP REQUEST message is rather trivial.

However, unlike LTE, NR/NG-RAN is by design capable of hosting cellsnumbering orders of magnitude larger than LTE. Specifically, it has beenagreed by the 3GPP RAN3 Working Group that the NR Cell Identity (NCI)parameter, which identifies a particular cell in a given network, can beup to and including 36-bits in length. The NCI parameter is composed totwo parts: (i) an gNB-ID value (identifier of the gNB itself), and (ii)a Cell Identity (identifier of a given cell). Furthermore, at RAN3#97bis(“Draft Report from the RAN WG3#97bis Meeting”, Prague, Czech Republic,9th-13th October 2017, v 1.0b, incorporated herein by reference in itsentirety), the working assumption of gNB-ID minimum length of 22-bits,and a maximum length being 32-bits, was utilized. Accordingly, thenumber of supported cells in an NG-RAN can be extremely high, e.g., upto 2¹⁴ (based on a maximum bit size of the NCI of 36 (as noted above),of which a minimum of 22 bits are required for gNB-ID—this allows for amaximum of 36−22=14 bits for cell identifiers, or 2{circumflex over( )}14 possible values).

Similar to the above-described S1 SETUP procedure, when the NG-RANemploys a “split” architecture—where gNB/ngeNB is split into (i) a CU(central or centralized unit) and (ii) a DU (distributed ordisaggregated unit)—an F1 SETUP interface setup procedure is used.

As a brief aside, and referring to FIG. 3, the CU 304 (also known asgNB-CU) is a logical node within the NR architecture 300 thatcommunicates with the NG Core 303, and includes gNB functions such astransfer of user data, session management, mobility control, RANsharing, and positioning; however, other functions are allocatedexclusively to the DU(s) 306 (also known as gNB-DUs) per various “split”options described subsequently herein in greater detail. The CU 304communicates user data and controls the operation of the DU(s) 306, viacorresponding front-haul (Fs) user plane and control plane interfaces308, 310.

Accordingly, to implement the Fs interfaces 308, 310, the (standardized)F1 interface is employed. It provides a mechanism for interconnecting agNB-CU 304 and a gNB-DU 306 of a gNB 302 within an NG-RAN, or forinterconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN.The F1 Application Protocol (F1AP) supports the functions of F1interface by signalling procedures defined in 3GPP TS 38.473. F1APconsists of so-called “elementary procedures” (EPs). An EP is a unit ofinteraction between gNB-CU and gNB-DU. These EPs are defined separatelyand are intended to be used to build up complete messaging sequences ina flexible manner. Generally, unless otherwise stated by therestrictions, the EPs may be invoked independently of each other asstandalone procedures, which can be active in parallel.

Within such an architecture 300, a gNB-DU 306 (or ngeNB-DU) is under thecontrol of a single gNB-CU 304. When a gNB-DU is initiated (includingpower-up), it executes the F1 SETUP procedure (which is generallymodeled after the above-referenced S1 SETUP procedures of LTE) to informthe controlling gNB-CU of, inter alia, the number of cells (togetherwith the identity of each particular cell) in the F1 SETUP REQUESTmessage. The gNB-CU at its discretion may choose to activate some or allcells supported by that gNB-DU, and even alter certain operationalparameters relating thereto, indicating these selections/alterations inthe F1 SETUP RESPONSE message. The identity of each cell to be activatedis also included in F1 SETUP RESPONSE.

As seen from the preceding discussion, as the number of cells supportedby a given gNB-DU increases, so does the message size of F1 Setupprocedure. Especially when the F1AP (the interface/protocol between thegNB-CU and a gNB-DU which it controls) is deployed over a constrainedbandwidth link (such as e.g., DOCSIS link of an MSO providing thebackhaul between the gNB-CU and a gNB-DU), significant “strain” isplaced on the available bandwidth of that constrained link, including tothe possible detriment of other services utilizing the same link.

Furthermore, because a single gNB-CU 304 can be deployed in acentralized location supporting hundreds to even thousands of gNB-DUs,the sheer amount of information (e.g., to configure the numerous F1APlinks corresponding to each served gNB-DU 306) transmitted over therespective links can itself result in network “flooding;” for instance,1,000 DOCSIS-supported links to a common gNB-CU may overwhelm thecapacity of the backhaul serving the gNB-CU within the network.

Currently, no viable mechanism for avoiding the foregoing overhead andcongestion exists. Accordingly, improved apparatus and methods areneeded to, inter alia, enable optimized activation of cells (e.g., thosesupported by respective gNB-DUs over the F1 interface).

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for providing optimized activation of cells,such as for example those supported by a NR/5G gNB-DU and gNB-CU.

In one aspect, a method for providing a wireless network node withefficient configuration messaging is disclosed. In one embodiment, themethod includes causing activation of a plurality of wireless cellsassociated with the network node via a centralized node using astreamlined configuration protocol.

In one variant, the wireless network comprises an NG-RAN, and thenetwork node includes at least one enhanced DU (DUe); when the F1interface is employed for the DUe with multiple cells, the servingenhanced CUe activates a plurality of cells of the DUe during an F1SETUP procedure using an aggregation mechanism. In one implementation,the aggregation mechanism comprises a single command, and advantageouslyobviates having to specify individual ID values for each activated cell,thereby reducing the overhead associated with the message(S). The F1SETUP procedure in one instance allows the activation of all cells of(under control of) the given DUe without specifically enumerating any ofthe cells to be activated. The F1 SETUP procedure in another instanceallows the activation of all cells of (under control of) the given DUewithout specifically providing any IDs (e.g., local or global cellidentifiers) of any of the cells to be activated.

In another variant, the CUe can enable a plurality of cells for each ofa plurality of DUe's under its control using a reduced number ofcommands, including in one implementation a single command.

In yet another variant, the CUe can enable a plurality of cells for eachof a plurality of DUe's, some under its direct control, and some undercontrol of another CU or CUe, using a reduced number of commands,including in one implementation a single command issued by the CUe.

In another aspect of the disclosure, network apparatus for use within awireless network is disclosed. In one embodiment, the network apparatusincludes a CUe entity, and is configured to at least cause activation ofa plurality of cells of one or more constituent DUes. In one variant,the CUe is disposed at a different geographic location than that of eachconstituent DUe, and the CUe and DUe(s) communicate via an MSO networkbackhaul.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, and includes aprogram memory or HDD or SSD on a computerized device such as a CUe. Inone variant, the one or more computer programs are configured to causegeneration of a command which, when transmitted by the CUe, causes oneor more receiving DUe's to activate a plurality of cells. The command isgenerated as part of a response to a DUe-to-CUe setup request.

In one implementation, the command is issued only to the recipient DUe.In another implementation, the command is issued to a prescribed subsetof the DUe's under control by the CUe. In yet another implementation,the command is issued globally to all DUs of the CUe. In yet a furtherimplementation, the command is issued to one or more DUs within “shared”infrastructure of another gNB.

In a further aspect, a wireless access node is disclosed. In oneembodiment, the node comprises a computer program operative to executeon a digital processor apparatus, and configured to, when executed,obtain data from a control entity with which the node is associated, andbased on the data, cause activation of a plurality of cells of the node.In one variant, the node is a DUe, and the data is part of a commandissued from the DUe's controlling CUe to invoke cell activationaccording to an F1 SETUP protocol.

In yet another aspect, a system is disclosed. In one embodiment, thesystem includes (i) a controller entity, (ii) one or more distributedentities in data communication therewith.

In still a further aspect of the disclosure, a method for mitigatingnetwork congestion is described. In one embodiment, the method includesidentifying one or more portions of a network infrastructure that areexperiencing congestion or are likely to experience congestion, andbased thereon, causing one or more messages exchanged between controllerand distributed wireless access node apparatus to utilize a streamlinedprotocol to reduce messaging overhead. In one variant, the networkinfrastructure comprises an MSO network backhaul infrastructure, and thestreamlined protocol comprises F1 SETUP REQUEST/RESPONSE messagingbetween the controller and distributed nodes using one or moreaggregated cell activation IE's.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a tabular representation of a prior art 3GPP LTE S1 SETUPrequest message and related parameters.

FIG. 2 is a tabular representation of a prior art 3GPP LTE S1 SETUPresponse message and related parameters.

FIG. 3 is a functional block diagram of a prior art gNB architectureincluding CU and multiple DUs.

FIG. 4a is a functional block diagram of one exemplary embodiment of agNB architecture including CU and multiple DUs, according to the presentdisclosure.

FIG. 4b is a functional block diagram of another exemplary embodiment ofa gNB architecture including multiple CUs and multiple correspondingDUs, according to the present disclosure.

FIG. 4c is a functional block diagram of yet another exemplaryembodiment of a gNB architecture including multiple CUs logicallycross-connected to multiple different cores, according to the presentdisclosure.

FIG. 5 is a functional block diagram of an exemplary MSO networkarchitecture useful in conjunction with various features describedherein.

FIG. 6 is a ladder diagram illustrating an exemplary embodiment of an F1startup and cell activation message flow according to the presentdisclosure.

FIGS. 6a-6b illustrate various implementations of exemplary cellactivation IEs (information elements) and associated protocols usefulwith the methodology of FIG. 6.

FIGS. 6a -1 and 6 a-2 illustrate an exemplary implementation of a globalcell identifier IE (information element) format and protocol useful withthe methodology of FIG. 6.

FIGS. 6b -1 and 6 b-2 illustrate various alternate implementations ofcell activation IE types and formats useful with various embodiments ofthe present disclosure.

FIG. 6c illustrates one implementation of exemplary cell de-activationIEs and associated protocols according to the present disclosure.

FIG. 7 is logical flow diagram of an exemplary method for cellactivation (or de-activation) according to the present disclosure.

FIG. 8 is a functional block diagram illustrating a first exemplaryembodiment of an enhanced distributed unit (DUe) apparatus useful withvarious embodiments of the present disclosure.

FIG. 9 is a functional block diagram illustrating a first exemplaryembodiment of an enhanced central(ized) unit (CUe) apparatus useful withvarious embodiments of the present disclosure.

All figures © Copyright 2017-2018 Charter Communications Operating, LLC.All rights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “central unit” or “CU” refers withoutlimitation to a centralized logical node within a wireless networkinfrastructure. For example, a CU might be embodied as a 5G/NR gNBCentral Unit (gNB-CU), which is a logical node hosting RRC, SDAP andPDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB thatcontrols the operation of one or more gNB-DUs, and which terminates theF1 interface connected with one or more DUs (e.g., gNB-DUs) definedbelow.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “distributed unit” or “DU” refers withoutlimitation to a distributed logical node within a wireless networkinfrastructure. For example, a DU might be embodied as a 5G/NR gNBDistributed Unit (gNB-DU), which is a logical node hosting RLC, MAC andPHY layers of the gNB or en-gNB, and its operation is partly controlledby gNB-CU (referenced above). One gNB-DU supports one or multiple cells,yet a given cell is supported by only one gNB-DU. The gNB-DU terminatesthe F1 interface connected with the gNB-CU.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices, orprovides other services such as high-speed data delivery and backhaul.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE),and other wireless data standards.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums. The term “MNO” asused herein is further intended to include MVNOs, MNVAs, and MVNEs.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications technologies or networkingprotocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay,3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, SGNR, WAP, SIP, UDP, FTP,RTP/RTCP, H.323, etc.).

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac/ax, 802.11-2012/2013 or 802.11-2016, aswell as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer(P2P) Specification”, incorporated herein by reference in its entirety).

Overview

In one exemplary aspect, the present disclosure provides improvedmethods and apparatus for providing enhanced wireless services which,inter alia, utilize efficient messaging and cell activation includingfor very large numbers of cells, and which do not overwhelm databackhaul(s) associated with wireless nodes used for communication.

In one embodiment, a message protocol is used wherein a prescribednumber of cells of a given DU (e.g., all, a prescribed subset, etc.) areactivated without having to enumerate or include specific data relatingto the cells being activated. In one variant, this “global” activationis conducted using an Activate All Cells IE (Information Element)disposed with the F1SETUP RESPONSE message issued by a controlling CUentity within a 5G (NR) infrastructure. Mechanisms for de-activation ofall cells are also disclosed.

In other variants, prescribed subsets of the total cell population areactivated/de-activated using prescribed IE structures and protocols.

In other variants, cells of multiple DUs can be controlledsimultaneously, such as via distribution of a system-wide globalactivation IE. In still further variants, broadcast or multicastdistribution of IE's is provided for, thereby enablingbandwidth-efficient activation/de-activation across larger swaths ofCU/DU infrastructure.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access nodes (e.g., gNBs) associated with or supported at leastin part by a managed network of a service provider (e.g., MSO and/or MNOnetworks), other types of radio access technologies (“RATs”), othertypes of networks and architectures that are configured to deliverdigital data (e.g., text, images, games, software applications, videoand/or audio) may be used consistent with the present disclosure. Suchother networks or architectures may be broadband, narrowband, orotherwise, the following therefore being merely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed service area, venue, orother type of premises), the present disclosure may be readily adaptedto other types of environments including, e.g., outdoors,commercial/retail, or enterprise domain (e.g., businesses), or evengovernmental uses. Yet other applications are possible.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Distributed gNB Architectures

Referring now to FIGS. 4a-4c , various embodiments of the distributed(CU/DU) gNB architecture according to the present disclosure aredescribed. As shown in FIG. 4a , a first architecture 400 includes a gNB402 having an enhanced CU (CUe) 404 and a plurality of enhanced DUs(DUe) 406. As described in greater detail subsequently herein, theseenhanced entities are enabled to permit efficient inter-processsignaling and cell activation, whether autonomously or under control ofanother logical entity (such as the NG Core 403 with which the gNBcommunicates, or components thereof).

The individual DUe's 406 in FIG. 4a communicate data and messaging withthe CUe 404 via interposed physical communication interfaces 408 andlogical interfaces 410. As previously described, such interfaces mayinclude a user plane and control plane, and be embodied in prescribedprotocols such as F1AP. Operation of each DUe and CUe are described ingreater detail subsequently herein; however, it will be noted that inthis embodiment, one CUe 404 is associated with one or more DUe's 406,yet a given DUe is only associated with a single CUe. Likewise, thesingle CUe 404 is communicative with a single NG Core 403, such as thatoperated by an MNO or MSO. Each NG Core 403 may have multiple gNBs 402associated therewith.

In the architecture 420 of FIG. 4b , two or more gNBs 402 a-n arecommunicative with one another via e.g., an Xn interface 407, andaccordingly can conduct at least CUe to CUe data transfer andcommunication. Separate NG Cores 403 a-n are used for control and userplane (and other) functions of the network.

In the architecture 440 of FIG. 4c , two or more gNBs 402 a-n arecommunicative with one another via e.g., the Xn interface 407, andaccordingly can conduct at least CUe to CUe data transfer andcommunication. Moreover, the separate NG Cores 403 a-n are logically“cross-connected” to the gNBs 402 of one or more other NG Cores, suchthat one core can utilize/control the infrastructure of another, andvice versa. This may be in “daisy chain” fashion (i.e., one gNB iscommunicative one other NG Core other than its own, and that NG Core iscommunicate with yet one additional gNB 402 other than its own, and soforth), or the gNBs 402 and NG Cores 403 may form a “mesh” topologywhere multiple Cores 403 are in communication with multiple gNBs ormultiple different entities (e.g., service providers). Yet othertopologies will be recognized by those of ordinary skill given thepresent disclosure. This cross-connection approach advantageously allowsfor, inter alia, sharing of infrastructure between two MNOs/MSOs, whichis especially useful in e.g., dense deployment environments which maynot be able to support multiple sets of RAN infrastructure.

It will also be appreciated that while described primarily with respectto a unitary gNB-CU entity or device 404 as shown in FIGS. 4a-4c , thepresent disclosure is in no way limited to such architectures. Forexample, the techniques described herein may be implemented as part of adistributed or dis-aggregated or distributed CU entity (e.g., onewherein the user plane and control plane functions of the CU aredis-aggregated or distributed across two or more entities such as a CU-C(control) and CU-U (user)), and/or other functional divisions areemployed.

It is also noted that heterogeneous architectures of eNBs or femtocells(i.e., E-UTRAN LTE/LTE-A Node B's or base stations) and gNBs may beutilized consistent with the architectures of FIGS. 4a-4c . Forinstance, a given DUe may act (i) solely as a DUe (i.e., 5G NR PHY node)and operate outside of an E-UTRAN macrocell, or (ii) be physicallyco-located with an eNB or femtocell and provide NR coverage within aportion of the eNB macrocell coverage area, or (iii) be physicallynon-colocated with the eNB or femtocell, but still provide NR coveragewithin the macrocell coverage area.

In the 5G NR model, the DU(s) 406 comprise logical nodes that each mayinclude varying subsets of the gNB functions, depending on thefunctional split option. DU operation is controlled by the CU 404 (andultimately for some functions by the NG Core 403). Split options betweenthe DUe and CUe in the present disclosure may include for example:

-   -   Option 1 (RRC/PCDP split)    -   Option 2 (PDCP/RLC split)    -   Option 3 (Intra RLC split)    -   Option 4 (RLC-MAC split)    -   Option 5 (Intra MAC split)    -   Option 6 (MAC-PHY split)    -   Option 7 (Intra PHY split)    -   Option 8 (PHY-RF split)

Under Option 1 (RRC/PDCP split), the RRC (radio resource control) is inthe CUe 404 while PDCP (packet data convergence protocol), RLC (radiolink control), MAC, physical layer (PHY) and RF are kept in the DUe,thereby maintaining the entire user plane in the distributed unit.

Under Option 2 (PDCP/RLC split), there are two possible variants: (i)RRC, PDCP maintained in the CUe, while RLC, MAC, physical layer and RFare in the DU(s) 406; and (ii) RRC, PDCP in the CUe (with split userplane and control plane stacks), and RLC, MAC, physical layer and RF inthe DUe's 406.

Under Option 3 (Intra RLC Split), two splits are possible: (i) splitbased on ARQ; and (ii) split based on TX RLC and RX RLC.

Under Option 4 (RLC-MAC split), RRC, PDCP, and RLC are maintained in theCUe 404, while MAC, physical layer, and RF are maintained in the DUe's.

Under Option 5 (Intra-MAC split), RF, physical layer and lower part ofthe MAC layer (Low-MAC) are in the DUe's 406, while the higher part ofthe MAC layer (High-MAC), RLC and PDCP are in the CUe 404.

Under Option 6 (MAC-PHY split), the MAC and upper layers are in the CUe,while the PHY layer and RF are in the DUe's 406. The interface betweenthe CUe and DUe's carries data, configuration, and scheduling-relatedinformation (e.g. Modulation and Coding Scheme or MCS, layer mapping,beamforming and antenna configuration, radio and resource blockallocation, etc.) as well as measurements.

Under Option 7 (Intra-PHY split), different sub-options for UL (uplink)and DL downlink) may occur independently. For example, in the UL, FFT(Fast Fourier Transform) and CP removal may reside in the DUe's 406,while remaining functions reside in the CUe 404. In the DL, iFFT and CPaddition may reside in the DUe 406, while the remainder of the PHYresides in the CUe 404.

Finally, under Option 8 (PHY-RF split), the RF and the PHY layer may beseparated to, inter alia, permit the centralization of processes at allprotocol layer levels, resulting in a high degree of coordination of theRAN. This allows optimized support of functions such as CoMP, MIMO, loadbalancing, and mobility.

The foregoing split options are intended to enable flexible hardwareimplementations which allow scalable cost-effective solutions, as wellas coordination for e.g., performance features, load management, andreal-time performance optimization. Moreover configurable functionalsplits enable dynamic adaptation to various use cases and operationalscenarios. Factors considered in determining how/when to implement suchoptions can include: (i) QoS requirements for offered services (e.g. lowlatency, high throughput); (ii) support of requirements for user densityand load demand per given geographical area (which may affect RANcoordination); (iii) availability of transport and backhaul networkswith different performance levels; (iv) application type (e.g. real-timeor non-real time); (v) feature requirements at the Radio Network level(e.g. Carrier Aggregation).

Service Provider Network—

FIG. 5 illustrates a typical service provider network configurationuseful with the features of the enhanced cell activation apparatus andmethods described herein. This service provider network 500 is used inone embodiment of the disclosure to provide backbone and backhaul fromthe service provider's service nodes, such as HFC cable or FTTC/FTTHdrops to different premises or venues/residences. For example. one ormore stand-alone or embedded DOCSIS cable modems (CMs) 512 are in datacommunication with the various NR architecture components (e.g., DUe'sand CUe's) as described in greater detail below, so as to providetwo-way data communication to the served components.

In certain embodiments, the service provider network 500 alsoadvantageously permits the aggregation and/or analysis of subscriber- oraccount-specific data (including inter alia, particular CUe or DUe orE-UTRAN eNB/femtocell devices associated with such subscriber oraccounts) as part of the provision of services to users under theexemplary delivery models described herein. As but one example,device-specific IDs (e.g., gNB ID, Global gNB Identifier, NCGI, MACaddress or the like) can be cross-correlated to MSO subscriber datamaintained at e.g., the network head end(s) 507 so as to permit or atleast facilitate, among other things, (i) user/device authentication tothe MSO network; (ii) correlation of aspects of the area, premises orvenue where service is provided to particular subscriber capabilities,demographics, or equipment locations, such as for delivery oflocation-specific or targeted content or advertising; and (iii)determination of subscription level, and hence subscriber privileges andaccess to certain services as applicable. Moreover, device profiles forparticular devices can be maintained by the MSO, such that the MSO (orits automated proxy processes) can model the device for wireless orother capabilities.

As a brief aside, a number of different identifiers are used in theNG-RAN architecture, including those of UE's and for other networkentities. Specifically:

-   -   the AMF Identifier (AMF ID) is used to identify an AMF (Access        and Mobility Management Function);    -   the NR Cell Global Identifier (NCGI), is used to identify NR        cells globally, and is constructed from the PLMN identity to        which the cell belongs, and the NR Cell Identity (NCI) of the        cell;    -   the gNB Identifier (gNB ID) is used to identify gNBs within a        PLMN, and is contained within the NCI of its cells;    -   the Global gNB ID, which is used to identify gNBs globally, and        is constructed from the PLMN identity to which the gNB belongs,        and the gNB ID;    -   the Tracking Area identity (TAI), which is used to identify        tracking areas, and is constructed from the PLMN identity to        which the tracking area belongs, and the TAC (Tracking Area        Code) of the Tracking Area; and    -   the Single Network Slice Selection Assistance information        (S-NSSAI), which is used to identify a network slice.        Hence, depending on what data is useful to the MSO or its        customers, various portions of the foregoing can be associated        and stored to particular gNB “clients” or their components being        backhauled by the MSO network.

The MSO network architecture 500 of FIG. 5 is particularly useful forthe delivery of packetized content (e.g., encoded digital contentcarried within a packet or frame structure or protocol) consistent withthe various aspects of the present disclosure. In addition to on-demandand broadcast content (e.g., live video programming), the system of FIG.5 may deliver Internet data and OTT (over-the-top) services to the endusers (including those of the DUe's 406 a-c) via the Internet protocol(IP) and TCP (i.e., over the 5G radio bearer), although other protocolsand transport mechanisms of the type well known in the digitalcommunication art may be substituted.

The network architecture 500 of FIG. 5 generally includes one or moreheadends 507 in communication with at least one hub 517 via an opticalring 537. The distribution hub 517 is able to provide content to various“client” devices 404 a-c, 406 a-c, and gateway devices 560 asapplicable, via an interposed network infrastructure 545. It will beappreciated from examination of FIG. 5 that the various gNB components(including DUe's and CUe's) may each act as a “client” device of thenetwork. For example, in many installations, the CUe 404 of a given gNBis physically disparate or removed from the locations of its constituentDUe's 406, and hence an interposed (e.g., wired, wireless, optical) PHYbearer is needed to communicate data between the DUe's and CUe of agiven gNB. In one such architecture, the CUe may be placed furthertoward the core of the MSO distribution network, while the variousconstituent DUe's are placed at the edge. Alternatively, both devicesmay be near the edge (and e.g., served by edge QAMs or RF carriers 540as shown in FIG. 5). In both cases, the MSO infrastructure may be usedto “backhaul” data from each device and communicate it to, via the MSOinfrastructure, the other components, much as two geographicallydisparate customers of a given MSO might communicate data via theirrespective DOCSIS modems in their premises. Each component has an IPaddress within the network, and as such can be accessed (subject to thelimitations of the architecture used as described above with respect toFIGS. 4a-4c ) by the other components.

Alternatively, the CUe's (which in effect aggregate the traffic from thevarious constituent DUe's towards the NG Core 403), may have a dedicatedhigh bandwidth “drop”.

Moreover, a given CU and DU may be co-located as desired, as shown bythe combined units 404 c, 406 c in FIG. 5. This may also be“hybridized,” such as where one constituent DUe is co-located (andpotentially physically integrated) with the CU, while the remaining DUeof that CUe are geographically and physically distributed.

In the MSO network 500 of FIG. 5, various content sources 503, 503 a areused to provide content to content servers 504, 505 and origin servers521. For example, content may be received from a local, regional, ornetwork content library as discussed in co-owned U.S. Pat. No. 8,997,136entitled “APPARATUS AND METHODS FOR PACKETIZED CONTENT DELIVERY OVER ABANDWIDTH-EFFICIENT NETWORK”, which is incorporated herein by referencein its entirety. Alternatively, content may be received from linearanalog or digital feeds, as well as third party content sources.Internet content sources 503 a (such as e.g., a web server) provideInternet content to a packetized content origin server(s) 521. Other IPcontent may also be received at the origin server(s) 521, such as voiceover IP (VoIP) and/or IPTV content. Content may also be received fromsubscriber and non-subscriber devices (e.g., a PC orsmartphone-originated user made video).

The network architecture 500 of FIG. 5 may further include a legacymultiplexer/encrypter/modulator (MEM; not shown). In the presentcontext, the content server 504 and packetized content server 521 may becoupled via a LAN to a headend switching device 522 such as an 802.3zGigabit Ethernet (or “10G”) device. For downstream delivery via the MSOinfrastructure (i.e., QAMs), video and audio content is multiplexed atthe headend 507 and transmitted to the edge switch device 538 (which mayalso comprise an 802.3z Gigabit Ethernet device) via the optical ring537.

In one exemplary content delivery paradigm, MPEG-based video content(e.g., MPEG-2, H.264/AVC) may be delivered to user IP-based clientdevices over the relevant physical transport (e.g., DOCSIS channels and5G NR bearer of the respective DUe 406); that is asMPEG-over-IP-over-MPEG. Specifically, the higher layer MPEG or otherencoded content may be encapsulated using an IP network-layer protocol,which then utilizes an MPEG packetization/container format of the typewell known in the art for delivery over the RF channels or othertransport, such as via a multiplexed transport stream (MPTS). Deliveryin such packetized modes may be unicast, multicast, or broadcast.

Individual devices such as cable modems 512 and associated gNB devices404, 406 of the implementation of FIG. 5 may be configured to monitorthe particular assigned RF channel (such as via a port or socketID/address, or other such mechanism) for IP packets intended for thegNB/subscriber premises/address that they serve. The IP packetsassociated with Internet services are received by edge switch, andforwarded to the cable modem termination system (CMTS) 539. The CMTSexamines the packets, and forwards packets intended for the localnetwork to the edge switch. Other packets are in one variant discardedor routed to another component.

The edge switch forwards the packets receive from the CMTS to the QAMmodulator, which transmits the packets on one or more physical(QAM-modulated RF) channels to the “client” gNB devices. The IP packetsare typically transmitted on RF channels that are different than the “inband” RF channels used for the broadcast video and audio programming,although this is not a requirement.

In one implementation, the CMs 512 shown in FIG. 5 each service apremises or venue, such as a conference center or hospitality structure(e.g., hotel), which includes one or more DUe nodes for provision of 5GNR services, and may also service WLAN (e.g., 802.11-2016 compliantWi-Fi) nodes for WLAN access (e.g., within 2.4 GHz ISM band), or evenE-UTRAN femtocells, CBRS (Citizens Broadband Radio Service) nodes, orother such devices.

In parallel with (or in place of) the foregoing delivery mechanisms, theMSO backbone 531 and other network components can be used to deliverpacketized content to the “client” gNB devices 404, 406 via non-MSOnetworks. For example, so-called “OTT” content (whether tightly coupledor otherwise) can be ingested, stored within the MSO's networkinfrastructure, and delivered to the gNB CUe 404 via an interposedservice provider network (which may include a public Internet) 511(e.g., at a local coffee shop, via a DUe connected to the coffee shop'sservice provider via a modem, with the user's IP-enabled end-user deviceutilizing an Internet browser or MSO/third-party app to stream contentaccording to an HTTP-based approach over the MSO backbone 531 to thethird party network to the service provider modem (or opticaldemodulator) to the DUe, and to the user device via the DUe NR wirelessinterface.

It will further be recognized that user-plane data/traffic may also berouted and delivered apart from the CUe. In one implementation(described above), the CUe hosts both the RRC (control-plane) and PDCP(user-plane); however, as but one alternate embodiment, a so-called“dis-aggregated” CUe may be utilized, wherein a CUe-CP entity (i.e.,CUe—control plane) hosts only the RRC related functions, and a CUe-UP(CUe—user plane) which is configured to host only PDCP/SDAP (user-plane)functions. The CUe-CP and CUe-UP entities can, in one variant, interfacedata and inter-process communications via an E1 data interface, althoughother approaches for communication may be used. It will also beappreciated that the CUe-CP and CUe-UP may be controlled and/or operatedby different entities, such as where one service provider or networkoperator maintains cognizance/control over the CUe-UP, and another overthe CUe-CP, and the operations of the two coordinated according to oneor more prescribed operational or service policies or rules.

In certain embodiments, each DUe 406 is located within and/or servicesone or more areas within one or more venues or residences (e.g., abuilding, room, or plaza for commercial, corporate, academic purposes,and/or any other space suitable for wireless access). Each DUe isconfigured to provide wireless network coverage within its coverage orconnectivity range for its RAT (e.g., 5G NR). For example, a venue mayhave a wireless NR modem (DUe) installed within the entrance thereof forprospective customers to connect to, including those in the parking lotvia inter alia, their NR or LTE-enabled vehicles or personal devices ofoperators thereof. Notably, different classes of DUe 406 may beutilized. For instance, by analogy, Class A LTE eNBs used in CBRSapplications can transmit up 30 dbm (1 watt), while Class-B LTE eNBs cantransmit up to 50 dbm, so the average area can vary widely. In practicalterms, a Class-A device may have a working range on the order ofhundreds of feet, while a Class B device may operate out to thousands offeet or more, the propagation and working range dictated by a number offactors, including the presence of RF or other interferers, physicaltopology of the venue/area, energy detection or sensitivity of thereceiver, etc. Similarly, different types of NR-enabled DUe 406 can beused depending on these factors, whether alone or with other wirelessPHYs such as LTE, WLAN, etc.

Methodology

Referring now to FIGS. 6-7, one embodiment of startup and cellactivation methodology of the present disclosure is now described indetail. This methodology is described in the exemplary context of theNGR F1 SETUP procedure referenced above, although it will be appreciatedthat it may be adapted to other procedures and applications by those ofordinary skill given the present disclosure.

Specifically, the illustrated methodology allows the setup of the F1interface between a DUe and a CUe, including activation of the desiredDUe cells. The purpose of the F1 SETUP procedure is to exchangeapplication level data needed for the DUe and the CUe to interoperatevia the F1 interface, and is the first F1AP procedure triggered afterthe TNL association has become operational. The F1 Setup procedure usesnon-UE associated signalling.

At step 602 of the methodology 600 of FIG. 6, the DUe and its cells areconfigured by OAM in the F1 pre-operational state. The DUe has TNLconnectivity toward the CUe.

At step 604, the DUe 406 sends an F1 SETUP REQUEST message to the CUe,including a list of cells that are configured and ready to be activated.As shown in FIG. 6a , this may be embodied in the form of a gNB-DUServed Cells List IE 620 and gNB-DU Served Cells Item IE 621, whichlists or enumerates the cells of the requesting DUe that have beenconfigured, up to the <maxCellingNBDU>622 value limit of e.g., 512(although other values may be used consistent with the presentdisclosure).

In one particular implementation, a “global” cell identificationmechanism is used for identification of individual cells. For instance,in one variant, a CGI (Cell Global Identifier) 624 of the type shown inFIG. 6a -1 is utilized, which includes a Cell Identity (CI) IE 626 (seeFIG. 6a -2), which is comprised of a multi-bit string of a prescribedlength (here, 36 bits, although more or less bits, and/or other IEstructures may be utilized consistent with the present disclosure, suchas the PCI or physical cell ID).

Returning again to the method 600 of FIG. 6, in the NG-RAN model, the CUensures the connectivity toward the core network 403. For this reason,the CUe 404 may initiate NG Setup or gNB Configuration Update procedurestowards the 5GC 403 as shown in step 606.

Next, per step 608, the CUe 404 sends an F1 SETUP RESPONSE message tothe requesting DUe 406 that optionally includes a “list” of cells to beactivated. As described in greater detail below, this list may beimplemented in any number of forms, including an IE (informationelement) which in one embodiment comprises an “Activate All Cells” IEincluded in the F1 SETUP RESPONSE message. The Activate All Cells IE maytake on any number of different forms, depending on CUe and DUeconfiguration. For example, in one variant (FIG. 6b ), the Activate AllCells IE activates all cells listed in the F1 SETUP REQUEST message fromthe DUe. This is in contrast to the prior art approach, wherein a DUactivates all the cells that are included in F1 SETUP REQUEST (and onlythose) via the Cells to be Activated List IE which includes a list ofcells that the CU requests the DU to activate.

If the DUe 406 succeeds in activating the cell(s) of the “list,” thenthese cells become operational. If the DUe fails to activate somecell(s), the DUe may initiate a DUe Configuration Update proceduretowards the CUe per step 608; in response, the CUe 404 may send a CUConfiguration Update message to the DUe that optionally includes a“list” of cells to activated (which may include the Activate All CellsIE)—e.g., in case that these cells were not activated using the F1 SETUPRESPONSE message of step 608.

Per step 612, the DUe 406 replies with a DUe Configuration UpdateAcknowledge message, that optionally may also include a list of cellsthat failed to be activated.

Per step 614, the CUe 404 may initiate Xn Setup or X2 Setup procedurestowards one or more neighbor gNBs 402 or eNBs, respectively.

It is further noted that in the case where the F1 SETUP RESPONSE is notused to activate any cell (e.g., where the CUe sends an F1 SETUPRESPONSE to the DUe 406 with no list), step 606 can be performed afterstep 608.

It is also noted that a “de-activation” function may be implementedconsistent with the present disclosure, such as de-active all or aprescribed subset of cells (analogous to the previously describedactivation messages and protocols). In one implementation, the CUe isconfigured to send a message (i.e., GNB-CU CONFIGURATION UPDATE)including a list or range of cells which the CUe wishes a particular DU(or set of DUs, in the case of a multicast/broadcast) to de-activate, asdescribed below in greater detail with respect to FIG. 6 c.

In one embodiment, the Activate All Cells IE 630 (FIG. 6b ) isconfigured to have two values; i.e., 0 (meaning do not activate “all”cells), and 1 (meaning activate “all” cells). Note that depending onimplementation, the definition of “all cells” that are to be activatedmay be varied. For instance, in one variant, the “all cells” is definedas “all cells included in the F1 SETUP REQUEST received from the DUe”(see FIG. 6b and discussion above relating thereto). Hence, in thiscase, the CUe will only mirror what cells are listed as “configured” bythe DUe in the F1 SETUP REQUEST message.

Alternatively, in other variants (see FIGS. 6b -1 and 6 b-2), the “allcells” of the IE may be a prescribed number or range of cells (e.g.,“C1-C512” or C_(n), where n=2^(i) to 2^(j)), irrespective of whetherthey have been listed by the DU or not. Multiple ranges of cells may bespecified such as through the use of a tiered IE system. For example, inone such approach, multiple Activate All Cells (IE_(n)) IEs 640 may bedefined, each one pertaining to a prescribed range (e.g., IE_(n=1) forcells 0-1024, IE_(n=5) for cells greater than a variable/prescribedvalue, and so forth); see FIG. 6b -1. In another variant (FIG. 6b -2),an “unconditional” activation 650 may be imposed by the CUe. Yet otherapproaches to specifying the definition of “all cells” will berecognized by those of ordinary skill given the present disclosure, theforegoing being merely exemplary species of the broader genus.

It will also be appreciated that the distributed/split architectures400, 420, 440 may be configured to utilize more global message and IEapproaches, thereby enabling common or concurrentactivation/de-activation of (i) multiple DUs served by a common CU, or(ii) multiple DUs served by two or more CUs. For example, a CU may beinstructed by its parent NGC 403 (or another NGC, such as in FIG. 4c )to activate all cells for all DUs which it controls. Likewise, a CU mayactivate all cells of its constituent DUs, as well as those of anotherCU with which it interfaces (i.e., via the Xn interface 407).

It will be recognized that under some prevailing implementations, it isthe DU which initiates F1 SETUP procedure. Until such initiation, thecorresponding CU has no knowledge of the DU's transport link (e.g., IPaddress). However, according to one embodiment of the presentdisclosure, the foregoing limitation is overcome by utilizing the OA&M(operation, administration and management)/EMS (element managementsystem) systems of the associated network to provision and update agiven DUe's transport link information. As such, after theprovisioning/update, a cognizant CUe can implement a protocol (e.g.,send a message e.g. F1-SETUP-UNSOLICITED or the like) to instruct all ofthe DUe's it has configured to “activate all cells” (or otherwise invokeactivation of a selected subset as described elsewhere herein). In oneapproach, the DUe's receiving such a message then use a defaultconfiguration which may be prestored on the DUe to activate the cells ithas configured, indicated in for example the “Activate All Cells” IE.

In another embodiment, the enhanced IE(s) (e.g., Activate All Cells) maybe modified to include one or more appended or additional data elements,such as for example where a physical cell identifier (PCI) requireschange for e.g., de-confliction purposes. In one implementation, the“Activate All Cells” IE includes cell-identifiers of cell(s) the CUewishes the DUe to modify (from its default configuration), along withlisting all the parameters it wishes for the DUe to modify (e.g. PCI inthe exemplary case), and process begins by activation of the cell(s)indicated via “Activate All Cells” IE on a “one-by-one” basis. Forinstance, in one implementation, a current cell in the list which the DUis working on activating (denoted as current cell to activate) is firstevaluated; if the cell-identifier of the current cell to activatematches the cell identifier of one of the IEs included in “Activate AllCells” IE, then the DUe (or its proxy) checks the list of modifiedattributes/parameters; these modified parameters are then utilized inthe activation procedure. The foregoing approach is then repeated untilcompliance with the “Activate All Cells” IE is achieved; i.e., all cellslisted in the IE are processed/dispositioned.

In yet other embodiments, the Activate All Cells IE(s) referenced abovecan be broadcast or multicast to two or more DUe's under control of agiven CUe, thereby obviating separate (unique) response messaging toeach DUe, and hence further reducing overhead (and congestion withine.g., the MSO backhaul or other communication channels). For instance, amulticast IP address format may be utilized (subject to the CUe knowingthe DUe transport(s), as previously discussed) to issue the command totwo or more DUe's; this may also be made contingent upon receipt ofrequest messaging (e.g., F1 SETUP REQUEST messages) from the constituentDUe's (e.g., where two DUe's simultaneously or nearly-simultaneouslyrequest setup per the F1AP, they can be contemporaneously activatedusing the enhanced IE's).

Referring now to FIG. 6c , one exemplary embodiment of a cellde-activation protocol (including IE's) according to the presentdisclosure is shown and described. In this embodiment, a GNB-CUCONFIGURATION UPDATE message is generated and sent by the CUe to one ormore DUe's transfer updated information for a TNL association. As shown,the relevant IE's of the message include a “Cells to be DeactivatedList” 662, configured as a “binary” or on/off value (0, 1), with cellsto be deactivated specifically listed in the “Cells to be DeactivatedList Item” 664 up to the <maxCellingNBDU> value 666 limit of e.g., 512(although other values may be used consistent with the presentdisclosure). Also note that in the illustrated embodiment, the “global”cell identification mechanism described supra with regard to cellactivation embodiments is used for identification of individual cells.For instance, in one variant, a CGI (Cell Global Identifier) of the typeshown in FIG. 6c is utilized, which includes a Cell Identity (CI) IE(see FIG. 6a -2), which is comprised of a multi-bit string of aprescribed length (here, 36 bits, although more or less bits, and/orother IE structures may be utilized consistent with the presentdisclosure).

Referring now to FIG. 7, one embodiment of a generalized methodology forefficient cell activation within a wireless network is disclosed. Itwill be appreciated that while described generally with respect to cellactivation, the methodology of FIG. 7 may also be readily adapted bythose of ordinary skill given the present disclosure to implementefficient cell de-activation for one or more DUe, consistent with theforegoing disclosure.

As shown in FIG. 7, the methodology 700 comprises first receiving aconfiguration request message at a first component of a distributedentity architecture at step 702. In one exemplary implementation, therequest message comprises an F1 SETUP REQUEST issued by the DUe 406 andtransmitted via the interface 408, 410 of the gNB architecture of FIG.4a to the CUe 404, and includes a Served Cells list of cells of the DUe.

Next, per steps 704 and 706, the receiving component (e.g., CUe 404)evaluates the IE(s) of the request message by extracting the datatherefrom, and analyzing it via computerized logic within the CUe (seeFIG. 9). In one embodiment, this analysis includes first determiningwhether the number of individual cells served by a given DUe 406 exceedsa prescribed threshold (e.g., greater than N). This can be accomplishedby, for example, consulting a database maintained by or accessible tothe CUe, or receiving such data in another message issued from e.g., anNG Core entity or controller. If N is exceeded (step 708), then one ormore of the enhanced IE(s) (e.g., Activate All Cells, Activate AllCells-n, etc.) is selected for use by the CUe logic per step 710.

If N is not exceeded per step 708, then the “list” approach of the priorart described above may be used (e.g., Cells to be Activated List IE)wherein cells are individually enumerated (step 712).

Once the relevant IE(s) have/has been selected, it/they are populatedwith the appropriate data per step 714, and the response containing thepopulated IE(s) transmitted to the requesting entity per step 716.

In one embodiment, the threshold “N” may be dynamically determined bythe CUe, the NGC 403, or yet another entity (such as a peercommunicative CUe as in FIG. 4b-4c ), or an MSO controller process. Forexample, in one variant, the various threshold (N) values for each DUewithin an MSO domain (e.g., backhauled by MSO infrastructure) areindividually determined by an MSO network computerized controllerprocess, which obtains loading data for various portions of MSO network(backhaul) infrastructure, and conducts algorithmic analysis thereof tomap the various portions of the MSO service topology which areexperiencing significant loading or “bottlenecking” (e.g., generallyakin to a highway traffic map indicating portions of roadwaysexperiencing reduced speeds/congestion). If say a certain portion,service group, or topological region of the MSO distribution network isexperiencing very high levels of DOCSIS bandwidth demand (upstreamand/or downstream, as relevant), then the controller might instruct allor a subset of affected CUes (i.e., those either: (i) served by theaffected MSO infrastructure, or (ii) having DUs over which they arecognizant, that are served by the affected infrastructure—see FIG. 5) toreduce their corresponding value of N, so that (i) fewer F1 SETUPREQUEST/RESPONSE message exchanges occur over those affected portions ofthe infrastructure, and (ii) the exchanges which do occur utilize lessbandwidth due to obviating the need for specific enumeration/descriptiondata for each cell.

These thresholds may also be programmatically implemented (e.g.,implemented according to a prescribed schedule and/orgeographic/topological region) or predictive/speculative in nature, suchas based on prior (historical) demand data as a function of date, time,or other parameter. In the case of such predictive or speculativethresholds, the CUe (or its proxy entity) may also schedule the cellactivation based on the prediction. For instance, if the predicted loadon a portion of the infrastructure of concern (e.g., the backhaulbetween one or more DUe's and the relevant CUe) is predicted to increaseor decline significantly over a current value at a prescribed futurepoint in time, the use of the reduced-overhead protocols describedherein can be selectively applied (or not applied, including “partial”application such as to only certain DUe of a given CUe, and/orreductions or increases in the threshold value of N) to coincide withthat future point in time, subject to any then-prevailing servicerequirements such as allowable latency for cell activation or the like.As but one example, the CUe may wait until other pending activationtransactions “clear” the system before implementing cell activation toone or more of its controlled DUe. Moreover, it will be appreciated thatthe CUe can notify or instruct the relevant DUe as to any schedulechanges or delays; e.g., such as via an IE in the setup responsemessage, whereby the DUe can postpone or delay activation based on thereceived IE.

Such analyses may also be conducted relative to or in consideration ofother CUe/DUe entities served by the MSO. For instance, where say three(3) different CUe's having DUe's backhauled by the MSO using affectedinfrastructure, these CUe's may be configured to communicate with oneanother (e.g., via the Xn interface) to coordinate use of cellactivation enhanced IEs.

It is further noted that while described herein as being in response toan F1 SETUP REQUEST message, the selection and use of the enhanced IEsmay be unsolicited, such as where the CUe desires to forcibly update orreconfigure one or more DUe's (e.g., to activate a large number of cellsconcurrently).

DUe Apparatus—

FIG. 8 illustrates an exemplary configuration of an enhanced distributedunit (DU_(e)) 406 according to the present disclosure. As shown, the DUe406 includes, inter alia, a processor apparatus or subsystem 802, aprogram memory module 804, mass storage 805, an HTTPS client andlocation function logic 806, one or more network interfaces 808, and oneor more RF (e.g., 5G/New Radio) PHY interfaces 809.

In the exemplary embodiment, the processor 802 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor 802 may also comprise an internal cachememory, and is in communication with a memory subsystem 804, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor 802.

The RF interface 809 is configured to comply with the relevant PHYstandards which it supports (e.g., 5G NR RAN, WLAN such as 802.11-16,and/or others as applicable) in the area/premises/venue being served.The antenna(s) 810 of the DUe NR radio may include multiple spatiallydiverse individual elements in e.g., a MIMO- or MISO-type configuration,such that spatial diversity of the received signals can be utilized.Moreover, a phased array or similar arrangement can be used for spatialresolution within the environment, such as based on time delaysassociated with signals received by respective elements.

The processing apparatus 802 is configured to execute at least onecomputer program stored in memory 804 (e.g., a non-transitory computerreadable storage medium); in the illustrated embodiment, such programsinclude DUe controller logic 806, such as whether to select an enhancedF1 SETUP REQUEST message IE or not, receipt and decode of the ActivateAll Cells or other enhanced IE, and other logical functions performed bythe DUe as described elsewhere herein. Other embodiments may implementsuch functionality within dedicated hardware, logic, and/or specializedco-processors (not shown). The DUe controller logic 806 is a firmware orsoftware module that, inter alia, communicates with a corresponding CUelogic portion (i.e., for message exchange and protocol implementation),and/or other upstream or backend entities such as those within the NGCore 403 in alternate embodiments.

In some embodiments, the DUe logic 806 utilizes memory 804 or otherstorage 805 configured to temporarily hold a number of data relating tothe various IE's (including Cell Lists) before transmission via thenetwork interface(s) 808 to the CUe 404 or NG Core 403. In otherembodiments, application program interfaces (APIs) such as thoseincluded in an MSO-provided application or those natively available onthe DUe may also reside in the internal cache or other memory 804. SuchAPIs may include common network protocols or programming languagesconfigured to enable communication with the DUe 406 and other networkentities (e.g., via API “calls” to the DUe by MSO network processestasked with gathering load, configuration, or other data). As an aside,a downloadable application or “app” may be available to subscribers ofan MSO or cable network (and/or the general public, including MSO“partner” MNO subscribers), where the app allows users to configuretheir DUe (or CUe as in FIG. 9 herein) to implement enhancedfunctionality, including data collection and reporting back to the MSOcore network so as to enable, inter alia, load determination,congestion, or other attributes which may be useful implementing e.g.,the methodology of FIG. 7 discussed above. Application programinterfaces (APIs) may be included in an MSO-provided applications,installed with other proprietary software that comes prepackaged withthe DUe. Alternatively, the relevant MNO may provide its subscriberswith the aforementioned functionality (e.g., as a pre-loaded app on theDUe at distribution, or later via download), or as a firmware update tothe DUe stack conducted OTA.

In one implementation, the MSO subscriber or client database may alsooptionally include the provisioning status of the particular DUe that isassociated with an MSO sub scriber.

It will be appreciated that any number of physical configurations of theDUe 406 may be implemented consistent with the present disclosure. Asnoted above, the functional “split” between DUe's and CUe has manyoptions, including those which may be invoked dynamically (e.g., wherethe functionality may reside in both one or more DUe's and thecorresponding CUe, but is only used in one or the other at a time basedon e.g., operational conditions).

CUe Apparatus—

FIG. 9 illustrates a block diagram of an exemplary embodiment of a CUe404 apparatus, useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the CUe 404 includes, inter alia,a processor apparatus or subsystem 902, a program memory module 904, CUecontroller logic 906 (here implemented as software or firmware operativeto execute on the processor 902), network interfaces 910 forcommunications and control data communication with the relevant DUe's414, and a communication with the NG Core 403 as shown win FIGS. 4a-4c ,as well as with other gNBs via the Xn interface 407. In one exemplaryembodiment, the CUe's 404 are maintained by the MSO and are eachconfigured to utilize a non-public IP address within an IMS/PrivateManagement Network “DMZ” of the MSO network. As a brief aside, so-calledDMZs (demilitarized zones) within a network are physical or logicalsub-networks that separate an internal LAN, WAN, PAN, or other suchnetwork from other untrusted networks, usually the Internet.External-facing servers, resources and services are disposed within theDMZ so they are accessible from the Internet, but the rest of theinternal MSO infrastructure remains unreachable or partitioned. Thisprovides an additional layer of security to the internal infrastructure,as it restricts the ability of surreptitious entities or processes todirectly access internal MSO servers and data via the untrusted network,such as via a CUe “spoof” or MITM attack whereby an attacker mightattempt to hijack one or more CUe to obtain data from the correspondingDUe's (or even UE's utilizing the DUe's).

Although the exemplary CUe 404 may be used as described within thepresent disclosure, those of ordinary skill in the related arts willreadily appreciate, given the present disclosure, that the “centralized”controller unit 404 may in fact be virtualized and/or distributed withinother network or service domain entities (e.g., within one of the DUe ofa given gNB 402, within the NG Core 403 or an MSO entity such as aserver, a co-located eNB, etc.), and hence the foregoing apparatus 404of FIG. 9 is purely illustrative.

In one embodiment, the processor apparatus 902 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor apparatus 902 may also comprise an internalcache memory. The processing subsystem is in communication with aprogram memory module or subsystem 904, where the latter may includememory which may comprise, e.g., SRAM, flash and/or SDRAM components.The memory module 904 may implement one or more of direct memory access(DMA) type hardware, so as to facilitate data accesses as is well knownin the art. The memory module of the exemplary embodiment contains oneor more computer-executable instructions that are executable by theprocessor apparatus 902. A mass storage device (e.g., HDD or SSD, oreven NAND flash or the like) is also provided as shown.

The processor apparatus 902 is configured to execute at least onecomputer program stored in memory 904 (e.g., the logic of the CUeincluding enhanced IE functionality and cell activation in the form ofsoftware or firmware that implements the various functions describedherein). Other embodiments may implement such functionality withindedicated hardware, logic, and/or specialized co-processors (not shown).

In one embodiment, the CUe 404 is further configured to register knowndownstream devices (e.g., access nodes including DUe's 406), other CUedevices), and centrally control the broader gNB functions (and anyconstituent peer-to-peer sub-networks or meshes). Such configurationinclude, e.g., providing network identification (e.g., to DUe's, gNBs,client devices such as roaming MNO UEs, and other devices, or toupstream devices such as MNO or MSO NG Core portions 403 and theirentities), and managing capabilities supported by the gNB's NR RAN.

The CUe may further be configured to directly or indirectly communicatewith one or more authentication, authorization, and accounting (AAA)servers of the network, such as via the interface 908 shown in FIG. 9.The AAA servers, whether locally maintained by the MSO or remotely bye.g., an MNO of the subscriber, are configured to provide services for,e.g., authorization and/or control of network subscribers (includingroaming MNO “visitors”) for controlling access and enforcing policies,auditing usage, and providing the information necessary to bill forservices.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A method of operating a wireless network having acontroller entity and at least one distributed wireless access node,comprising selectively utilizing a modified setup procedure to activateat least a number (N) of wireless cells of the at least one distributedwireless access node, the modified setup procedure having reducedoverhead as compared to a normal setup procedure used when a number ofwireless cells to be activated is less than N.
 2. The method of claim 1,wherein: the controller entity comprises a NR (New Radio)-compliantcentralized unit (CU); the at least one distributed wireless access nodecomprises a NR (New Radio)-compliant distributed unit (DU); and theutilizing the modified setup procedure comprises using at least oneInformation Element (IE) configured to activate the at least N wirelesscells without having to specify particular cell ID data.
 3. The methodof claim 2, wherein the activation of the at least N wireless cellscomprises activating all cells of the DU.
 4. The method of claim 2,further comprising receiving a configuration request message from the atleast one DU, the configuration request message comprising data relatingto at least a portion of the at least N wireless cells; and wherein theat least one Information Element (IE) is configured to activate or notactivate the at least portion of the at least N wireless cells based atleast in part on the data.
 5. The method of claim 2, wherein the CUcomprises: (i) a CU-CP (CU Control plane) entity, and (ii) a CU-UP(CU-User Plane) entity, and the utilizing the modified setup procedurecomprises the CU-CP only using the at least one Information Element (IE)configured to activate the at least N wireless cells without having tospecify particular cell ID data.
 6. The method of claim 2, furthercomprising using at least one Information Element (IE) configured tode-activate a plurality of wireless cells without having to specifyparticular cell ID data.
 7. The method of claim 1, wherein theactivation of the at least N wireless cells occurs contemporaneously,and the at least one wireless access node is configured to identify allof the at least N wireless cells based only on receipt of a commandtransmitted from the controller entity, the command not identifying anyspecific wireless cells.
 8. The method of claim 1, wherein the at leastone wireless access node comprises a plurality of wireless access nodes,each of the plurality of wireless access nodes configured to identifyall of the at least N wireless cells based only on receipt of a commandtransmitted from the controller entity, the command not identifying anyspecific cells, the command broadcast to each of the plurality ofwireless access nodes contemporaneously.
 9. A method of operating awireless network having at least one controller entity and a pluralityof distributed wireless access nodes under control thereof so as toreduce load on one or more network backhaul portions between the atleast one controller entity and the plurality of distributed wirelessaccess nodes, the method comprising: determining a number of cellsassociated with one or more of the plurality of distributed wirelessaccess nodes to be activated; evaluating, using at least onecomputerized process, the number; based at least in part on saidevaluating, causing selection of a non-cell specific communicationprotocol between the at least one controller entity and the plurality ofdistributed wireless access nodes; configuring an information element(IE) for use in the non-cell specific communication protocol; andtransmitting at least the configured IE to the one or more of theplurality of distributed wireless access nodes to cause activation ofthe number of cells associated with one or more of the plurality ofdistributed wireless access nodes.
 10. The method of claim 9, wherein:the controller entity comprises a NR (New Radio)-compliant centralizedunit (CU); the plurality of distributed wireless access nodes comprisesa plurality of NR (New Radio)-compliant distributed units (DUs); and thedetermining a number of cells comprises: receiving a setup requestmessage from each of the one or more of the plurality of distributedwireless access nodes; and extracting data relating to the number fromeach of the setup request messages received.
 11. The method of claim 9,wherein at least the evaluating is performed by a computerized processof a network operator entity, the one or more network backhaul portionsbetween the at least one controller entity and the plurality ofdistributed wireless access nodes operated by the network operatorentity, the network operator entity different than an entity whichoperates: (i) the at least one controller entity, and (ii) the pluralityof wireless access nodes.
 12. The method of claim 9, wherein theevaluating comprises using a computerized process of the at least onecontroller entity to compare the number to a threshold value.
 13. Themethod of claim 12, wherein the method further comprises dynamicallydetermining the threshold value prior to the comparison, the dynamicallydetermining comprising evaluating data associated with then-current loadof the one or more network backhaul portions.
 14. The method of claim12, wherein the method further comprises: dynamically determining thethreshold value prior to the comparison, the dynamically determiningcomprising generating data associated with a projection or prediction offuture level of load of the one or more network backhaul portions;utilizing the dynamically determined threshold value as part of thecomparison at a then-current time; and based at least on the comparison,causing the transmitting of at least the configured IE at a future timeconsistent with the projection or prediction.
 15. The method of claim14, wherein the projection or prediction is based at least in part onanalysis of pending messaging or communications between the at least onecontroller and the plurality of wireless access nodes via the one ormore network backhaul portions.
 16. The method of claim 9, wherein thecausing selection of a non-cell specific communication protocol betweenthe at least one controller entity and the plurality of distributedwireless access nodes comprises causing selection of a protocol whichuses an aggregated IE which does not require specific enumeration oridentification of each of the number of cells to be activated.
 17. Acomputerized network controller entity for use in a wirelessinfrastructure, the computerized network controller entity comprising:digital processing apparatus; at least one data network interface indata communication with the digital processing apparatus; and a storagedevice in data communication with the digital processing apparatus, thestorage device comprising a storage medium having at least one computerprogram, the at least one computer program configured to, when executedon the digital processing apparatus, cause the computerized networkcontroller entity to: receive messaging via the data network interface,the messaging received according to a prescribed network communicationprotocol an including one or more request messages issued by at leastone distributed wireless access point under at least partial control ofthe computerized network controller entity; extract data from themessaging, the extracted data relating to a plurality of wireless cellsassociated with the at least one distributed wireless access point;cause algorithmic evaluation of the extracted data to determine that afirst computerized protocol for activation of the plurality of wirelesscells should be utilized instead of a second, default protocol foractivation of the plurality of cells; based at least on a result of thealgorithmic analysis, cause utilization of the first computerizedprotocol to activate the plurality of cells, the activation of theplurality of cells using the first computerized protocol comprising:specifying a first information element (IE) configured to cause the atleast one distributed wireless access point to utilize a prescribedsecond IE for determining which of the plurality of cells to activate;specifying one or more values for the second IE; and causingtransmission of a response message to the at least one distributedwireless access point, the response message comprising at least thefirst IE and the second IE.
 18. The computerized network controllerentity of claim 17, wherein: the one or more request messages compriseone or more NR (New Radio) compliant F1 SETUP REQUEST messages; theresponse message comprises a NR compliant F1 SETUP RESPONSE message; andthe first and second IE's comprise a binary state value and a numericrange, respectively.
 19. The computerized network controller entity ofclaim 18, wherein use of the binary state value and the numeric rangecooperate to obviate having to list the plurality of cells individually.20. The computerized network controller entity of claim 19, wherein theobviation of having to list the plurality of cells individuallycomprises obviation of listing the plurality of cells by a unique cellID.